-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NEP-485: Shared Ephemeral Storage #485
base: master
Are you sure you want to change the base?
Conversation
Your Render PR Server URL is https://nomicon-pr-485.onrender.com. Follow its progress at https://dashboard.render.com/static/srv-ci68bj5gkuvkf1netopg. |
- How long should the code live in SES before it expires? | ||
- How would SES integrate with dynamic sharding? | ||
- What happens when you `FUNCTION_CALL` a SES contract that references expired code? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you clarify/outline the motivation for expiring contract code (why expiring is needed, and what are the alternatives) ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the code doesn't expire, there's no guarantee that its storage will be paid for, but the validators are still required to keep it alive.
Hello! Protocol NEP moderator here. it seems there hasn't been any activity on this NEP for quite some time. Is it still on going? Or shall we close NEP for now? cc. @encody |
Another ping on status of this NEP. As more than two months have passed since the last activity, if we don't hear back from the author by December 4th, we will mark the NEP as retracted for now. Thanks- |
I will assume this NEP is inactive and label as retracted for now. If anyone picks the NEP up again, please ping NEP moderators to make it active. |
No description provided.